Skip to main content

Endpoint Management Overview

The new Endpoint Management pages replace the previous Endpoint Sensors page, where you configured Deployment Groups and other sensor settings. The new pages provide customer-manageable Profiles and reusable Configurations under the Endpoints section of the console. This new structure is designed to offer greater flexibility, granular control over device settings, and dynamic policy application.

Understanding the Redesign: Comparison of Old vs. New Concepts​

The redesign fundamentally changes how you manage device configurations. In the legacy structure, deployment groups were managed through a complex editor and required manual device assignment. The new modular system is built for reusability and dynamic assignment.

The following table provides a comparison of the old vs. new concepts, showing you how the old system translates into the new system.

Old ConceptNew ConceptFunction in the Redesign
Deployment GroupsProfilesThe central object that bundles configurations and defines Dynamic Targeting rules to assign policies to matching devices.
Monolithic SettingsConfigurationsReusable modules of settings (e.g., Policy, Detection, Performance). These are created once and linked to multiple Profiles.
Manual TargetingDynamic TargetingThe system automatically assigns devices to the correct Profile based on rule criteria (e.g., OS, Host Name) upon registration, eliminating the need for custom installer commands.
JSON Remote ConfigOverridesA dedicated field within a Profile for entering advanced, low-level settings using flattened JSON. Overrides supersede all settings in linked Configurations.

The Endpoints section organizes all sensor management functions into clear, specialized pages:

  • Profiles: Create and manage profile objects that bundle reusable configurations, define dynamic targeting rules, set priority, and provide a summary of endpoint health/connectivity; includes per‑profile uninstall protection and optional overrides.
  • Endpoints: View devices registered to the tenant and, within profiles, see counts, issues, OS distribution, and activity to understand which endpoints match which profile.
  • Configurations: Build reusable settings in five categories—Content Inspection, Detection, Performance, Policy, and Software Updates—that can be attached to multiple profiles.
  • Installers: Access the installer command/strings used to deploy the sensor; profile assignment no longer requires a deployment‑group tag because dynamic targeting applies after registration.

Migration of Existing Deployment Groups​

The platform automatically handles the transition of your existing environment to ensure continuity of service with minimal disruption.

  • Immutability: Each existing Deployment Group was converted into an immutable "migrated" profile with a Priority of 0.

  • Settings Preservation: The full configuration settings of the original Deployment Group are preserved and stored as a set of flattened JSON overrides within the new Profile.

  • Continuity: Migrated profiles continue to apply to their existing, hardcoded lists of devices, ensuring no settings are lost and policies remain in effect.

Required Action: Since migrated profiles are immutable, you must duplicate them or create new Profiles using the Configurations to modify or update any settings going forward.